Dynomotion

Group: DynoMotion Message: 8028 From: yeamans115 Date: 7/30/2013
Subject: win7 i think kills kmotion?
machined all day and now I go back to the machine and windows keeps getting a "not responding" error after a minute of so of cutting.
kflop is still connected though.
what makes this not respond?

on a side note for some reason once a new g code is run for the first time there is a lag of nothing after hitting the cycle start button on the kmotion screen. this seems to be fast on some programs and slow on others.
whats up with that?

I just loaded up the 4.30m to see if that changes anything and I don't think it did. 4.30e was the old.
do I need to delete the older folder or will it run the newest one on its own?

thanks matt
Group: DynoMotion Message: 8029 From: yeamans115 Date: 7/30/2013
Subject: Re: win7 i think kills kmotion?
--- In DynoMotion@yahoogroups.com, "yeamans115" <yeamans115@...> wrote:
>
> machined all day and now I go back to the machine and windows keeps getting a "not responding" error after a minute of so of cutting.
> kflop is still connected though.
> what makes this not respond?
>
> on a side note for some reason once a new g code is run for the first time there is a lag of nothing after hitting the cycle start button on the kmotion screen. this seems to be fast on some programs and slow on others.
> whats up with that?
>
> I just loaded up the 4.30m to see if that changes anything and I don't think it did. 4.31e was the old.
> do I need to delete the older folder or will it run the newest one on its own?
>
> thanks matt
>
Group: DynoMotion Message: 8033 From: Tom Kerekes Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
Hi Matt,

Not sure.  That would indicate KFLOP is somehow locked up.  What is the minimum you need to do to restore operation?  Possibilities are Noise, Power supply glitch, or Software bug.

Regarding Cycle Start Delay:  I assume you meant to say KMotionCNC?  Are you saying there is a lag on the first time but not the 2nd?  Or from one Job to a different Job?  There is a small delay depending on the speed of your PC, USB data rate, complexity of the beginning of the GCode path, and the amount of Data Buffering that you have specified to need. 

Those Test Versions are both older than V4.30.  You do not need to delete older KMotion Folders.

Regards
TK


Group: DynoMotion Message: 8037 From: yeamans115 Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
I think noise and power supply are not the issue.

yes, kmotioncnc. yep. first run seems to always have some thinking time and then it starts to move.?

got a link to the newest version?

thanks matt

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Matt,
>
> Not sure.  That would indicate KFLOP is somehow locked up.  What is the minimum you need to do to restore operation?  Possibilities are Noise, Power supply glitch, or Software bug.
> Regarding Cycle Start Delay:  I assume you meant to say KMotionCNC?  Are you saying there is a lag on the first time but not the 2nd?  Or from one Job to a different Job?  There is a small delay depending on the speed of your PC, USB data rate, complexity of the beginning of the GCode path, and the amount of Data Buffering that you have specified to need. 
>
>
> Those Test Versions are both older than V4.30.  You do not need to delete older KMotion Folders.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: yeamans115 <yeamans115@...>
> To: DynoMotion@yahoogroups.com
> Sent: Tuesday, July 30, 2013 10:10 PM
> Subject: [DynoMotion] win7 i think kills kmotion?
>
>
>
>  
> machined all day and now I go back to the machine and windows keeps getting a "not responding" error after a minute of so of cutting.
> kflop is still connected though.
> what makes this not respond?
>
> on a side note for some reason once a new g code is run for the first time there is a lag of nothing after hitting the cycle start button on the kmotion screen. this seems to be fast on some programs and slow on others.
> whats up with that?
>
> I just loaded up the 4.30m to see if that changes anything and I don't think it did. 4.30e was the old.
> do I need to delete the older folder or will it run the newest one on its own?
>
> thanks matt
>
Group: DynoMotion Message: 8038 From: Tom Kerekes Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
Hi Matt,

The Latest Release Code is listed on the website download page.  But here it is again:

http://dynomotion.com/Software/KMotion430.exe

The latest test release is V4.31i


I'm still not clear on the delay.  Is it:

A - the first run after the first time a file is loaded, but no delay on a second run of the same file?

or

B - running some Jobs always have an initial delay and other Jobs never have a delay?


How big is the Delay?  Did what I describe match what you are seeing?

Maybe your USB transfer rate is slow on your PC for some reason?  You can run \KMotion\Release\SimpleFormsCS.exe and push the TEST USB button to test your rate.  My PC shows:

PC->KFLOP N=100000 Int32, Time=4.144 sec, 214KBytes/sec
KFLOP->PC N=100000 Int32, Time=5.097 sec, 174KBytes/sec

Regards
TK

Group: DynoMotion Message: 8039 From: yeamans115 Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
A is it.
the delay seems to vary a lot. sometimes 1-2 seconds and other times maybe 5-8 seconds.
I will try the test after lunch.
thanks matt

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Matt,
>
> The Latest Release Code is listed on the website download page.  But here it is again:
>
> http://dynomotion.com/Software/KMotion430.exe
>
>
> The latest test release is V4.31i
>
> http://dynomotion.com/Software/KMotion431i.exe
>
>
> I'm still not clear on the delay.  Is it:
>
> A - the first run after the first time a file is loaded, but no delay on a second run of the same file?
>
> or
>
> B - running some Jobs always have an initial delay and other Jobs never have a delay?
>
>
> How big is the Delay?  Did what I describe match what you are seeing?
>
> Maybe your USB transfer rate is slow on your PC for some reason?  You can run \KMotion\Release\SimpleFormsCS.exe and push the TEST USB button to test your rate.  My PC shows:
>
> PC->KFLOP N=100000 Int32, Time=4.144 sec, 214KBytes/sec
>
> KFLOP->PC N=100000 Int32, Time=5.097 sec, 174KBytes/sec
>
>
> Regards
> TK
>
>
> ________________________________
> From: yeamans115 <yeamans115@...>
> To: DynoMotion@yahoogroups.com
> Sent: Wednesday, July 31, 2013 10:52 AM
> Subject: [DynoMotion] Re: win7 i think kills kmotion?
>
>
>
>  
> I think noise and power supply are not the issue.
>
> yes, kmotioncnc. yep. first run seems to always have some thinking time and then it starts to move.?
>
> got a link to the newest version?
>
> thanks matt
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Matt,
> >
> > Not sure.  That would indicate KFLOP is somehow locked up.  What is the minimum you need to do to restore operation?  Possibilities are Noise, Power supply glitch, or Software bug.
> > Regarding Cycle Start Delay:  I assume you meant to say KMotionCNC?  Are you saying there is a lag on the first time but not the 2nd?  Or from one Job to a different Job?  There is a small delay depending on the speed of your PC, USB data rate, complexity of the beginning of the GCode path, and the amount of Data Buffering that you have specified to need. 
> >
> >
> > Those Test Versions are both older than V4.30.  You do not need to delete older KMotion Folders.
> >
> > Regards
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: yeamans115 <yeamans115@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Tuesday, July 30, 2013 10:10 PM
> > Subject: [DynoMotion] win7 i think kills kmotion?
> >
> >
> >
> >  
> > machined all day and now I go back to the machine and windows keeps getting a "not responding" error after a minute of so of cutting.
> > kflop is still connected though.
> > what makes this not respond?
> >
> > on a side note for some reason once a new g code is run for the first time there is a lag of nothing after hitting the cycle start button on the kmotion screen. this seems to be fast on some programs and slow on others.
> > whats up with that?
> >
> > I just loaded up the 4.30m to see if that changes anything and I don't think it did. 4.30e was the old.
> > do I need to delete the older folder or will it run the newest one on its own?
> >
> > thanks matt
> >
>
Group: DynoMotion Message: 8043 From: yeamans115 Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
hey, I deleted the older version and it took out my parameters/settings in the kmotion cnc.

I still have the old version in the trashcan, is there a file I can just copy and paste back into the new version to reset all my stuff back to where it was?
thanks matt
Group: DynoMotion Message: 8045 From: Tom Kerekes Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
Hi Matt,

Most all settings are stored in the <Install Directory>\KMotion\Data folder.

Normally when installing a new version you would copy the files in this data directory to the new version.

Deleting the older directory should have no effect on the new directory or version.

Are you sure you really were running the new version?

You should always keep a backup of your working Data and Program Files.

Regards
TK



Group: DynoMotion Message: 8048 From: yeamans115 Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
great, I got my settings in place and seems to be correct.

speed test looks much different than yours.
PC->KFLOP N=100000 Int32, Time=12.511 sec, 71KBytes/sec
KFLOP->PC N=100000 Int32, Time=15.274 sec, 58KBytes/sec


right when I hit the test button windows says not responding for a moment and then the test results come back.?
Group: DynoMotion Message: 8050 From: Tom Kerekes Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
Hi Matt,

That does seem slow.  You might try a different port.  Is this a USB3 port?  Are you going through a Hub or anything?

Also you never answered my questions on how much buffering you have specified.  Or the nature of your GCode.

Regards
TK

Group: DynoMotion Message: 8051 From: yeamans115 Date: 7/31/2013
Subject: Re: win7 i think kills kmotion?
i am not sure of the usb quality.
this goes right into a usb on the desktop.
buffering? I got 5 seconds in the trajectory planner....
Gcode is made by dolphin cad/cam.
everything I do is simple with no crazy stuff.
thanks matt

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Matt,
>
> That does seem slow.  You might try a different port.  Is this a USB3 port?  Are you going through a Hub or anything?
>
> Also you never answered my questions on how much buffering you have specified.  Or the nature of your GCode.
>
> Regards
> TK
>
>
> ________________________________
> From: yeamans115 <yeamans115@...>
> To: DynoMotion@yahoogroups.com
> Sent: Wednesday, July 31, 2013 3:11 PM
> Subject: [DynoMotion] Re: win7 i think kills kmotion?
>
>
>
>  
> great, I got my settings in place and seems to be correct.
>
> speed test looks much different than yours.
> PC->KFLOP N=100000 Int32, Time=12.511 sec, 71KBytes/sec
> KFLOP->PC N=100000 Int32, Time=15.274 sec, 58KBytes/sec
>
> right when I hit the test button windows says not responding for a moment and then the test results come back.?
>